The "Microsoft Office Professional Plus encountered an error during setup." and "Microsoft Setup Bootstrapper has put to work." messages are displayed

Hi

I have the MSDN DVD of Office SP1 Professional Plus 2013 32/64 bit .

When I try to install the 32 bit or 64 bit version on Windows 7 Enterprise SP1 64 bit, the "Microsoft Office Professional Plus encountered an error during setup." and "Microsoft Setup Bootstrapper has put to work." messages are displayed. Why?

Thanks

Bye

May 20th, 2015 4:57am

Examine the setup logfiles at %TEMP% - this may reveal to you the nature of the errors encountered.

Others have had success, in similar situations, by navigating into the architecture-specific sub-folders (either 32bit or 64bit) and execute the setup.exe located in there (instead of using setup.exe in the root folder)

Free Windows Admin Tool Kit Click here and download it now
May 20th, 2015 5:25am

Examine the setup logfiles at %TEMP% - this may reveal to you the nature of the errors encountered.

Others have had success, in similar situations, by navigating into the architecture-specific sub-folders (either 32bit or 64bit) and execute the setup.exe located in there (instead of using setup.exe in the root f

May 20th, 2015 6:13am

I've already done all the tests that you said but the same error messages are displayed.

Here is a log file:

2015/05/20 09:21:54:216::[968] PERF: TickCount=932558 Name=OBootStrapper::Run Description=Begin function
2015/05/20 09:21:54:216::[968] Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2
2015/05/20 09:21:54:216::[968] Running 64-bit setup on a 64-bit operating system.
2015/05/20 09:21:54:216::[968] Command line: "\\PIPPO\Seconda_unita_virtuale\x64\setup.exe" 
2015/05/20 09:21:54:216::[968] No command line arguments given
<.....>
2015/05/20 09:23:40:844::[2500] Determining ARP entry registry values. 2015/05/20 09:24:11:717::[2500] Error: MsiBeginTransaction failed. MsiBeginTransaction ErrorCode: 1601(0x641). 2015/05/20 09:24:11:732::[2500] WER element [P4] is set to value [1601] 2015/05/20 09:24:11:732::[2500] WER element [P7] is set to value [1601] 2015/05/20 09:24:11:732::[2500] WER element [P6] is set to value [%s %s] 2015/05/20 09:24:11:732::[2500] WER element [P6] is converted to [FC73469E] 2015/05/20 09:24:11:732::[968] Showing completion dialog. 2015/05/20 10:18:11:975::[968] Reboot requested if needed. 2015/05/20 10:18:11:975::[968] No reboot is needed. 2015/05/20 10:18:11:990::[968] Catalyst execution finished: 05/20/2015 10:18:11. Return code: 1601. 2015/05/20 10:18:11:990::[968] PERF: TickCount=4310260 Name=RunSetup Description=End function

It is helpful to mention to us, the things you have already tried - it saves time ;)

It's also helpful to mention when you are attempting 32bit-on-64bit, or 64bit-on-64bit ;)

So, from the logfile you supplied, the setup process is returning 1601 error (the windows installer could not be accessed or another installation is already in progress).

1601 could be thrown because some other process is running, blocking windows installer (windows installer is typically an exclusive process it will not start a second installation if another installation is already executing, or, another installation had not flagged completion properly, or previously crashed)

1601 could be thrown because windows installer, or other dependencies within windows, are damaged or improperly configured.

You will need to research msiexec 1601 error examples and scenarios.

Or, if this machine is not healthy (windows), repair the machine to good health.

As a test, can you install any other software (software which uses msiexec/windows installer) with success?

Free Windows Admin Tool Kit Click here and download it now
May 20th, 2015 5:30pm

I've already done all the tests that you said but the same error messages are displayed.

Here is a log file:

2015/05/20 09:21:54:216::[968] PERF: TickCount=932558 Name=OBootStrapper::Run Description=Begin function
2015/05/20 09:21:54:216::[968] Operating System version: 6.1.7601 Service Pack 1. Platform ID: 2
2015/05/20 09:21:54:216::[968] Running 64-bit setup on a 64-bit operating system.
2015/05/20 09:21:54:216::[968] Command line: "\\PIPPO\Seconda_unita_virtuale\x64\setup.exe" 
2015/05/20 09:21:54:216::[968] No command line arguments given
<.....>
2015/05/20 09:23:40:844::[2500] Determining ARP entry registry values. 2015/05/20 09:24:11:717::[2500] Error: MsiBeginTransaction failed. MsiBeginTransaction ErrorCode: 1601(0x641). 2015/05/20 09:24:11:732::[2500] WER element [P4] is set to value [1601] 2015/05/20 09:24:11:732::[2500] WER element [P7] is set to value [1601] 2015/05/20 09:24:11:732::[2500] WER element [P6] is set to value [%s %s] 2015/05/20 09:24:11:732::[2500] WER element [P6] is converted to [FC73469E] 2015/05/20 09:24:11:732::[968] Showing completion dialog. 2015/05/20 10:18:11:975::[968] Reboot requested if needed. 2015/05/20 10:18:11:975::[968] No reboot is needed. 2015/05/20 10:18:11:990::[968] Catalyst execution finished: 05/20/2015 10:18:11. Return code: 1601. 2015/05/20 10:18:11:990::[968] PERF: TickCount=4310260 Name=RunSetup Description=End function

It is helpful to mention to us, the things you have already tried - it saves time ;)

It's also helpful to mention when you are attempting 32bit-on-64bit, or 64bit-on-64bit ;)

So, from the logfile you supplied, the setup process is returning 1601 error (the windows installer could not be accessed or another installation is already in progress).

1601 could be thrown because some other process is running, blocking windows installer (windows installer is typically an exclusive process it will not start a second installation if another installation is already executing, or, another installation had not flagged completion properly, or previously crashed)

1601 could be thrown because windows installer, or other dependencies within windows, are damaged or improperly configured.

You will need to research msiexec 1601 error examples and scenarios.

Or, if this machine is not healthy (windows), repair the machine to good health.

As a test, can you install any other software (software which uses msiexec/windows installer) with su

May 21st, 2015 2:59am

The Office CD is not corrupt as I tried to install it on Windows 8.x 64 bit and it works.

Thanks

Bye

Free Windows Admin Tool Kit Click here and download it now
May 21st, 2015 1:06pm

This article may assist you to diagnose the setup failure:
http://blogs.technet.com/b/odsupport/archive/2010/12/30/troubleshooting-office-installation-failures.aspx
May 21st, 2015 5:25pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics